 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| july 1998 1/42 rev. 1.01 ST7MDT1-DVP development kit for st72251g1/g2, st72101g1/g2, st72212g2 and st72213g1 mcus preface purpose of the manual this manual describes how to start and use the ST7MDT1-DVP development kit for the st72251g2 series mcus, allowing you to get acquainted with the st7 microcontroller world and become familiar with the methods for developing and debugging st7-driven applications. the st72251g2 covers the st72101g1/g2, st72212g2, st72213g1 and st72251g1/g2 mcus the manual also provides a guidance for programming a selection of st7 microcontrollers, in eprom or one time programmable (otp) mode. audience this book is intended for persons: ? who wish to evaluate how to design and test applications using st7 microcontrollers, ? who want to use the ST7MDT1-DVP development kit to meet their actual application development needs. no preliminary knowledge in the field of microcontrollers is required. related publications the following publications contain useful complementary information: ? st7-family, data sheets , ? st7-family, 8-bit mcus, product overview , ref. bkst7/2 ? software tools for the st7 family , ref. doc-st7asmlk-sw ? st7-family, programming manual , ? windows debugger for the st7 family , doc-st7-wgdb7. this manual will help you debug and finalize your programs. 15
2/42 table of contents 42 16 ST7MDT1-DVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 what the development kit affords you . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1 a wide range of functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.2 package description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.3 board functional configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.4 development board layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2 what you can do with the development kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.1 preliminary contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.1.1 connect and power up the development board . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.1.2 install and setup the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.2 start working with the development kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3 getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.1 hardware installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.1.1 antistatic requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.1.2 powering up the evaluation board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.2 software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.3 using the st assembly chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.4 starting the wgdb7 debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.5 programming st7 devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.5.1 target devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 9 3.6 device installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.6.1 starting the windows epromer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.6.2 configuring the epromer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 4 hardware features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 4.1 emulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 4.1.1 general layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 4.1.2 cpu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 4.1.3 clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 4.1.4 memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 4.1.5 on-chip peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 4.1.6 hardware breakpoint capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 4.1.7 input trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.1.8 external output trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.2 connection to external user resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.2.1 pin description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.2.2 supplying the application board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.2.3 limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 4.3 device programmer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 4.3.1 general layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 4.3.2 targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 4.4 link to pc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 4.5 power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 3/42 table of contents 5 software features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 5.1 tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 5.2 st assembly chain for st7 family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 5.3 hiware c compiler demonstration chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 5.4 st7 simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 5.5 st7 windows debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 5.6 epromer for st7 mcus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 17 4/42 ST7MDT1-DVP standard compliance this product is conform to the 89/336/eec directive. it complies with the en55022 emissions standard for ite and generic 50082-1 immunity standards. organization of the manual this manual comprises five chapters and an index: chapter 1, what the develop- ment kit af- fords you, provides a general description of the components of the development kit. chapter 2, what you can do with the develop- ment kit, is a quick introduction to the develop- ment kit. chapter 3 , getting start- ed , explains how to in- stall and use the components of the development kit. chapter 5 , software fea- tures , discusses the soft- ware tools that are included in the de- velopment kit. chapter 4, hard- ware fea- tures, introduc- es you to the emu- lator and the de- vice programmer. index 18 5/42 ST7MDT1-DVP 1 what the development kit affords you 1.1 a wide range of functions the ST7MDT1-DVP development kit for the st72251g2 series mcus contains all the nec- essary resources that will help you: ? design, ? develop, ? debug st7 application software running in a real environment, ? and program st72101g1/g2, st72212g2, st72213g1 and st72251g1/g2 devices in both eprom and otp modes. note: these functions are currently available for devices with sdip32 packages. you may however use devices with so28 packages by adding the appropriate zif socket on the board (see development board layout on page 9). 1.2 package description the ST7MDT1-DVP development kit package contains: hardware ? one development board with a cable for pc connection (ref. mb 212/b), ? one sdip32 passive probe (ref. db 320/a) and one 34-pt flat cable for user application connection, ? one 5 v external dc power supply with cable, table 1. st72251g2 series summary device rom ram a/d timer spi i2c st72101g1 4k 256 no 1x16 bits yes no st72101g2 8k 256 no 1x16 bits yes no st72213g1 4k 256 6x8 bits 1x16 bits yes no st72212g2 8k 256 6x8 bits 2x16 bits yes no st72251g1 4k 256 6x8 bits 2x16 bits yes yes st72251g2 8k 256 6x8 bits 2x16 bits yes yes 19 6/42 ST7MDT1-DVP ? 2 st72251g2 mcu samples, ? one cd rom and disks for documentation and software. the board is connected through a parallel port interface to a pc used to monitor debugging and device programming operations. software and documentation the cd-rom and the disks contain: ? the present guide, ? an emulator-aided debugger, ? software tools, comprising a source-level debugger operating with the development board or an st7 simulator, an assembler, a linker, an st7 eprom programmer, and associated user documentation, ? a basic c-compiler, for demonstration purposes only, ? a device epromer, ? st7 application notes, with sources. figure 1. software/hardware structure of the ST7MDT1-DVP development kit st7 emulator st7 program- ming socket other hardware elements connector to pc connector to user application board hardware software assembly toolchain st7 simulator wgdb7 debugger windows epromer 20 7/42 ST7MDT1-DVP figure 2. ST7MDT1-DVP development kit general configuration 1.3 board functional configurations the development board of the ST7MDT1-DVP development kit can be used as an st7 mcu emulator or as an st7 mcu programming board, as shown in the figures next page. 21 8/42 ST7MDT1-DVP figure 3. using the development board as an st7 mcu emulator figure 4. using the development board as an st7 mcu programming board 22 9/42 ST7MDT1-DVP 1.4 development board layout warning the ST7MDT1-DVP development kit board is a class-a apparatus. in a residential environ- ment, it may cause radioelectrical disturbances. also, the the ST7MDT1-DVP development kit board is not contained in an outer casing; consequently, it cannot be immune against elec- trostatic discharges (esd). it should therefore be handled only in static safe working areas. external power supply other power inlet control ram emulation ram eprom device program- ming socket sdip32 zif so28 zif space for device progra- mming socket ground 5v power outlet for user appli led (red) board power on led (green ) application connector external trigger input external trigger output pld demonstration board supply 34-pin he10 prog run external clock input st72331e cpu pld 16 mhz clock parallel port connector if you want to supply your application directly from the board, via the appli- cation connector, place a solder spot here (g1 vcc app). max 100 ma. 23 10/42 ST7MDT1-DVP 2 what you can do with the development kit 2.1 preliminary contacts lets suppose that you have just unpacked your ST7MDT1-DVP development kit. youre eager to try it. try it now! 2.1.1 connect and power up the development board 1 connect the development board (p2 connector) to the parallel port (lpt1 or lpt2) of your pc via the appropriate cable. 2 connect the probe (p3 connector) using the flat cable that has been supplied in the package. 3 power up the board. watch! the green power led lights up. 2.1.2 install and setup the software 1 insert the delivery cd rom into your cd rom drive. 2 using windows explorer, open the root directory of your cdrom drive 3 double-click welcome.pdf. watch! the welcome window opens: click here 24 11/42 ST7MDT1-DVP 1 click st7 tools on the welcome window. the st7 tool chain setup introductory window appears on your screen. click next to continue. 2 in the next window, choose destination location , click next to continue (using the default folder (or directory) for the software to be loaded to. 3 in the next window, select components , click the wgdb7 debugger and develop- ment kit , st assembler chain and windows epromer check boxes. leave other check boxes empty. click next to continue. 4 the next window, check setup information , displays the settings you have speci- fied: click next to confirm. 5 the copying process takes place. watch! a progress indicator keeps you informed of the status of the operation. when the cop- ying process terminates, you are directed to the setup complete window. 2.2 start working with the development kit from now on, you can do whatever you want in the scope of your development activities. you can: ? code your applications using the st assembly chain , ? debug your applications using the wgdb7 debugger with either the st7 simulator (no hardware needed), the emulator, or the development board, ? program any st72251g2 series device with the application you just developed, using the windows epromer software. to start any of these tools, just click the corresponding icon (or name in the cascading menus) in the windows desktop. note: chapter 3, getting started , will provide you with more detailed information on how to start a session, and how to activate the tools. 25 12/42 ST7MDT1-DVP 3 getting started 3.1 hardware installation 3.1.1 antistatic requirements 3.1.1.1 testers and tools any tester, equipment, or tool used at any production step or for any manipulation of semi- conductor devices must have its shield connected to ground. 3.1.1.2 antistatic equipment an antistatic equipment should comprise: ? a conductive table top, made of steel or clean aluminium or covered by an antistatic sur- face (superficial resistivity equal to or higher than 0.5 megohm/cm2), grounded through a ground cable (conductive cable from protected equipment to ground isolated through a 1- megohm resistor placed in series). ? an antistatic floor covering grounded through a conductive ground cable (with serial resis- tor between 0.9 and 1.5 megohm). 3.1.1.3 manipulation of finish goods manipulation of finish goods must be made at a grounded worktable. it is mandatory to wear an antistatic wrist or ankle strap, connected to the antistatic floor cov- ering or to the grounded equipment. it is mandatory to wear antistatic gloves or finger coats. nylon clothing is prohibited during manipulation of parts. the worktable must be free of any non antistatic plastic objects. the wearing of the antistatic strap must be controlled every day. 3.1.2 powering up the evaluation board proceed as follows: 1 connect the evaluation board (p2 connector) to the parallel port (lpt1 or lpt2) of your pc via the appropriate cable. note: the supplied interface cable has been tested in order to operate properly on most pcs. do not use any other cable, especially if it is longer than the one provided by stmicroelectronics: the board may not operate properly. the cable should be connected directly to the db-25 female connector of the pc par- allel port. this connector is similar to the one installed on the board. do not insert any 26 13/42 ST7MDT1-DVP additional cables or switchboxes between the pc and the board: a malfunctioning of the board may result. if a dongle is mounted on the pc parallel port, it should not interfere with the program- ming board. should you notice a dysfunctioning of the board, remove the dongle and restart the installation procedure. 2 connect the probe (p3 connector) using the flat cable that has been supplied in the package. 3 power up the board. note: the board can also be fed via the jp1 connector by an external stabilized power sup- ply (5v 0.25 v, 1 a) not provided with the kit. if the board is fed via the jp1 two-point connector make sure that the right feeders lead to the right polarities. the green power led lights up. 3.2 software installation to install and setup the ST7MDT1-DVP development kit software, follow these steps: 1 insert the delivery cd-rom into your cd-rom drive. 2 using windows explorer, open the root directory of your cdrom drive. table 2. if then... acrobat reader is already installed on your system. double-click welcome.pdf. when the welcome screen is displayed, click st7 tools acrobat reader is not yet installed on your system 1. open the program folder/acrobat3/ 2. select and install the appropriate language version of acrobat (for more details refer to the readme.txt in the cdrom root directory) 3. when acrobat is installed double-click welcome.pdf. when the welcome screen is displayed, click st7 tools 27 14/42 ST7MDT1-DVP the st7 tool chain setup introductory window appears on your screen, referring to the three software components of the ST7MDT1-DVP development kit: ? wgdb7 debugger ? st assembly chain for the st7 family ? st7 epromer click next to continue. 3 in the next window, choose destination location , you will specify the folder (or di- rectory) where to copy the whole ST7MDT1-DVP development kit software. use the default folder (or directory) or choose another folder (or directory): click here 28 15/42 ST7MDT1-DVP click next to continue. 4 in the next window, select components , you will select the software components that are to be copied from the cd-rom into the folder (directory) you specified be- fore. note: if you select the development kit, it is not necessary to select the hds emulator at the same time (dont check the corresponding box). click here to select another path this is the default path return to previous window continue installation process abort installation process 29 16/42 ST7MDT1-DVP click next to continue. 5 the next window, check setup information , displays the settings you have speci- fied: ? ? destination folder (directory) ? ? components to be installed click next to confirm. click back to change any settings. 6 the copying process takes place. a progress indicator keeps you informed of the status of the operation. when the copying process terminates, and if you didnt select the st assembly chain as a component for the installation, you are directed to the setup complete window (see further on). if you selected the st assembly chain , you are prompted to modify your autoexec.bat file (or your system registry). these changes affect: ? the pat h option, where the path for the components of the assembly chain should be added, ? the metai and dos4g environment variables that have to be set to the following val- return to previous window continue installation process abort installation process to select a component, check the appropriate box selectin g the wgdb7 debu gg er cause these subcomponents to be displa y ed select the development kit version of the wgdb7 debu gg er 30 17/42 ST7MDT1-DVP ues, respectively: set metai=c:\ 18/42 ST7MDT1-DVP c:\st7tools\asm for more information on how to develop applications or programs for the st7 microcontroller, refer to the software tools for the st7 family user manual included in the cd-rom. 3.4 starting the wgdb7 debugger the wgdb7 debugger is installed in the installation root directory. by default, you will find it in: c:\st7tools to start wgdb7, just click the wgdb7 development kit icon (or name in the cascading men- us) in the windows desktop. the wgdb7 introductory window appears: note: to start wgdb7 with the simulator you would only click the wgdb7 simulator icon or name in the cascading menus in the windows desktop. similarly, to start wgdb7 with the emulator you would only click wgdb7 emulator in the windows desktop. the debugging session starts a few seconds later. to get accustomed to the product, you may start one of the sample programs provided with the package, via the file/open debugger menu chain. the sample programs can be found in: c:\ 19/42 ST7MDT1-DVP 3.5 programming st7 devices 3.5.1 target devices once bug-free and ready for operation, the program you just developed needs to be trans- ferred into an st7 mcu program space. with the ST7MDT1-DVP development kit, you may program these mcus (*): st72101 g1 or g2 st72212 g2 st72213 g1 st72251 g1 or g2 (*) this list is subject to modifications we recommend that you practise device programming using one of the sample mcus provid- ed with the ST7MDT1-DVP development kit. 3.6 device installation place the device into the zero insertion force socket (zif) socket mounted on the board (loca- tion u19 for sdip32 devices) with the erasure window on top and pin 1 matching the mark on the board. note: you may also use so28 devices by adding the appropriate zif socket on the board on the footprint provided at location u17. the reference number of the socket (not supplied with the kit) is emplas ots 28-1.27-04 . caution placing the device into a socket without care may damage the device or the board. never insert or remove devices when supplied. devices are supplied only during read or write operations. 3.6.1 starting the windows epromer the windows epromer (winee) is installed in the epromer directory. by default, you will find it in: c:\st7tools\epromer to start the windows epromer, just click the corresponding icon (or name in the cascading menus) in the windows desktop. the epromer main window appears: 33 20/42 ST7MDT1-DVP 3.6.2 configuring the epromer follow these steps: 1 in the main window tool bar, click the icon to select the epromer configuration window: click here to displa y the epromer confi g uration window note that as lon g as the pro g rammin g board and the device to be pro g rammed are not specified, the displa y area is blank. 34 21/42 ST7MDT1-DVP 2 2in the list, select the programming board for this ST7MDT1-DVP development kit: ST7MDT1-DVP 3 click the select chip tab to display the list of the devices that can be programmed with this ST7MDT1-DVP development kit. the list box shown below appears. 35 22/42 ST7MDT1-DVP 4 in the list, select the device to be programmed: st72101g1 or g2 st72212g2 st72213g1 st72251g1 or g2 click ok to confirm. the list box closes. the memory mapping of the specified device now appears in the display area of the main window. it is made up of ffs, as one may expect, since programming has not taken place yet. to view in turn the memory mapping of a selection of devices plugged in, open the config- uration window again, then the select chip list box, and click apply . the display area of the main window changes while the list box stays open, for you to choose another chip if necessary. 36 23/42 ST7MDT1-DVP 5 start your programming session. for more information on how to use the windows epromer, click the help command in the main menu bar. the name of the device to be pro g rammed is displa y ed here details stored in the epromer buffer for the the eprom has been selected space correspondin g to the currentl y selected tab pppppp pro g ress bar (pro g ress of the current task bein g executed b y the epromer) cursor position in the displa y area ori g in of the displa y area contents information area displa y area 37 24/42 ST7MDT1-DVP 4 hardware features 4.1 emulator 4.1.1 general layout 38 25/42 ST7MDT1-DVP 4.1.2 cpu the board is equipped with an st72331e cpu that can operate in two different modes: the user mode and the system mode. when in user mode, the cpu is entirely devoted to the processing of your application code. it therefore behaves as the cpu of the target microcontroller you speci- fied beforehand, via the appropriate debugger command sequence: - wgdb7 main menu - command s menu - micro name command (see windows debugger for the st7 family, user manual ). when your application program is running the ld1 red led lights up. when in system mode, the cpu is used to execute all other tasks. when you select a command in the main menu of the debugger, you cause the cpu to auto- matically switch from one mode to the other. specifying the target microcontroller selecting any of these commands in the windows debugger causes the cpu to switch to the user mode. main window selecting this command causes the cpu to switch to the system mode. all other windows debugger commands execute in system mode only. 39 26/42 ST7MDT1-DVP 4.1.3 clock the development board is shipped with a 16-mhz (ttl) in- ternal clock. you may also use an external clock (ttl-compatible, max 16 mhz) whose signal is supplied via the mini wrapping pin clockin located on the board next to the passive probe flat connector (ref.: tp18). caution: in normal mode (miscellaneous register slow mode bit = 0), ac- ceptable clockin frequencies can take any value between 16 mhz and 250 khz. in slow mode (miscellaneous register slow mode bit = 1), the clockin frequency must take values between 16 mhz and 8 mhz. note that the board cannot operate with clock signals received from the application board via the oscin pin of the probe. you must use the clockin inlet instead. by contrast, the application board can use the development board clock via the oscout pin of the probe. in this case you must place a solder spot on g2 (see table 4, probe pin assign- ment (sdip32), on page 32). a debugger dialog box lets you choose the clock type ( internal or external ) as a microcontrol- ler configuration option. you access these dialog boxes via the following debugger command sequence: - wgdb7 main menu - command s menu - micro configuration command (see windows debugger for the st7 family, user manual ). 40 27/42 ST7MDT1-DVP 4.1.4 memory the memory mapping for the emulated device is also configurable. you access this dialog boxes via the following debug- ger command sequence: - wgdb7 main menu - command s menu - memory configura- tion command (see windows debug- ger for the st7 family, user manual ). this feature would ena- ble you, for instance, to temporarily increase the rom size during the de- velopment phase of your application. in the example, a r0m area has been mapped to the d000h-dfffh part of a reserved area (0180h-dfffh) for the target device (st72212g2). 4.1.5 on-chip peripherals parallel i/o ports 22 bidirectional parallel i/o lines with interrupts are supported. the i/o lines can be shared be- tween other on-chip peripherals (alternate functions) and any general purpose i/o function de- fined by the application. data is input and output via data registers (one for each port). data direction and option registers allow each line to be individually configured to the application's requirements. 16-bit timers two 16-bit timers, timer a and timer b, are available (st72212 g2 and st7225 g1/g2 only; the other devices supported by the ST7MDT1-DVP development kit use timer a only). they consist of a 16-bit free-running counter driven by a programmable prescaler. both timers fea- ture output compare, pulse width modulation (pwm) and input capture functions with associ- ated registers. this allows applications to measure pulse intervals or generate pulse wave- 41 28/42 ST7MDT1-DVP forms. timer overflow and other events are flagged in a status register with optional interrupt generation. a debugger dialog box lets you en- able/disable the clocks for timer a or timer b as a microcontroller con- figuration option. when the disabled option is cho- sen, the timer is frozen as long as the cpu operates in system mode. for instance, you would use this option to check whether the timer has reached a specified val- ue. when the enabled option is cho- sen, the timer is continuously oper- ating even in system mode. an example of use of this option is for an application in which the pwm (pulse width modulation) output of the timer drives a motor that must keep running. analog to digital converter the adc peripheral multiplexes up to 8 analog input channels. it converts the analog input to 8-bit value using monotonic successive approximation. the analog input voltage must lie with- in the supply voltage range, which is used as the analog reference. spi serial peripheral interface the spi peripheral is a synchronous serial interface for master and slave device communica- tions. single master and multimaster mode systems are supported for communication with ex- ternal peripherals or other microprocessors. dedicated registers and interrupts allow full soft- ware control and user defined protocols. 42 29/42 ST7MDT1-DVP watchdog timer the watchdog timer consists of a 7-bit reloadable downcounter that triggers a device reset if it reaches a predefined value. during normal operation, the application reloads the counter at regular intervals to prevent a reset occurring. by this means, if the application hangs, the con- dition is automatically cleared by reset- ting the mcu. the watchdog timer can be enabled by software or by hardware. the choice is a microcontroller configuration option. i 2 c bus interface the i 2 c bus is a synchronous serial bus for connecting multiple devices using a data line and a clock line. the st7 i 2 c interface operates in multimaster or slave mode and supports speeds of up to 400 khz. bus events (bus busy, slave address recognised) and error condi- tions are automatically flagged in peripheral registers and interrupts are optionally generated. the interface supports 7 and 10-bit addressing. 4.1.6 hardware breakpoint capabilities with the ST7MDT1-DVP development kit you can define hardware breakpoints that cause your program to stop whenever a defined event occurs. an event can be: ? the occurrence of a memory access via a read operation ? the occurrence of a memory access via a write operation ? the occurrence of an opcode fetch ? the occurrence of a write operation in a write-protected location ? the occurrence of a write operation in a reserved location ? the occurrence of a stack overflow/underflow ? the occurrence of an access to a reserved memory area ? the occurrence of a external input signal (triggered break feature). the signal is conveyed via a mini wrapping pin located on the board next to the passive probe flat connector. 43 30/42 ST7MDT1-DVP 4.1.7 input trigger the evaluation board of the ST7MDT1-DVP development kit provides a special inlet (tri- gin, ref.:tp18) that can be used to transmit a signal to stop the execution of your application upon the occurrence of an external event. in this case, the program is stopped after the exe- cution of the current instruction. the corresponding diagram is as follows: a debugger dialog box lets you choose the waveform mode for the external signal ( pulse mode or windows mode ) as a microcontroller configuration option (see windows debug- ger for the st7 family, user manual ). 4.1.8 external output trigger the evaluation board of the st7mdt-dvp development kit features a special outlet through which an external signal can be triggered out. the signal is conveyed via a mini wrapping pin located on the board next to the passive probe flat connector (ref.: tp16). a debugger dialog box lets you choose the waveform mode for the external signal ( pulse mode or windows mode ) as a microcontroller configuration option (see windows debug- ger for the st7 family, user manual ). 4.2 connection to external user resources 4.2.1 pin description you may connect an application board to the st7mdt-dvp development kit evaluation board for evaluation or debugging in linked emulation mode. the p3 connector in the evalua- tion board provides all the i/o pins needed for the communication. signals are transmitted via a passive probe to be plugged in the application board at the location of the emulated device. monitor application phi 1 op code fetch trigin trigin active on rising edge 44 31/42 ST7MDT1-DVP table 2 shows the pin assignment for the p3 connector (evaluation board) and the probe (ap- plication board). table 3. p3 pin assignment for probe connection (34-pin he10) description p3 pin no. p3 pin no. description application reset 1 2 application vcc ground 3 4 a0 port oscout 5 6 a1 port ground 7 8 a2 port b7 port 9 10 a3 port b6 port 11 12 ground b5 port 13 14 a4 port b4 port 15 16 ground b3 port 17 18 a5 port b2 port 19 20 ground b1 port 21 22 a6 port b0 port 23 24 ground c5 port 25 26 a7 port c4 port 27 28 c0 port c3 port 29 30 c1 port ground 31 32 ground ground 33 34 c2 port 45 32/42 ST7MDT1-DVP (*) the emulator clock is connected to oscout only when a solder spot is placed in g2 on the evaluation board. (**) application voltage: 4.5 to 5.5 v only. 4.2.2 supplying the application board there are two ways in which you may supply your application board directly from the evalua- tion board: table 4. probe pin assignment (sdip32) pin name/description probe pin no. probe pin no. pin name/description reset 1 17 c2 port not used (oscin) 2 18 c1 port oscout (*) 3 19 c0 port b7 port 4 20 a7 port b6 port 5 21 a6 port b5 port 6 22 a5 port b4 port 7 23 a4 port not used 8 24 not used not used 9 25 not used b3 port 10 26 a3 port b2 port 11 27 a2 port b1 port 12 28 a1 port b0 port 13 29 a0 port c5 port 14 30 not used (vpptest) c4 port 15 31 vss (gro und) c3 port 16 32 vdd (**) 46 33/42 ST7MDT1-DVP 1 by using the two test pins located in tp14 (gnd) and tp15 (5v) on the evaluation board. then the current should not exceed 100 ma. 2 via the vdd pin in the p3 probe connector, after a solder spot has been placed in g1 on the evaluation board. this method is not recommended. 4.2.3 limitations ? the minimum cpu operating internal frequency of the development board is 250 khz (for more details, see clock on page 26. ? the application supply voltage should take a value between 4.5 and 5.5 v, different from the 3-6 v range for the devices. ? if any of the pb1 or pc1 ports are to be used for a pwm output it is recommended to insert an fct circuit between the output pin and the application side, as in the following example: caution electrical levels and behaviour on i/o port pins depend on the technology used in the pld (programmable logic device) referred to as epf 10k30 on the development board. the technology used is ttl-compatible, different from the st72251 chip technology (cmos). consequently, electrical high state levels on i/o pins are limited to 3.3 v. pb1 74fct244 analog output 47 34/42 ST7MDT1-DVP 4.3 device programmer 4.3.1 general layout 4.3.2 targets the evaluation board provides you with the necessary resources to program an st7 device belonging to the st72251g2 series: st72101g1 or g2, st72251g1 or g2, st72213g1, or st72212g2. the sample device supplied with the ST7MDT1-DVP development kit is accommodated by the sdip32 zero insertion force (zif) socket mounted on the board (ref.: u19). 4.4 link to pc the ST7MDT1-DVP development kit evaluation board communicates with your pc via the p2 connector connected to the pc parallel port (lpt1 or lpt2). note: the parallel port of your pc should have been configured as a centronics parallel 48 35/42 ST7MDT1-DVP port (bios settings). the development kit does not support epp, ecp or bidirection- al parallel port configurations. 4.5 power supply a plug-in power supply pack is supplied with the ST7MDT1-DVP development kit to be con- nected to the p1 female jack connector. this power supply must be plugged into the appropri- ate ac source. specific sales types indicate the corresponding mains ac voltage supported: 220v, 110v (us), or 240v (uk). provided dc power specifications are as follow: voltage: 5 v current: 1 a a complementary power supply inlet (ref. jp1) is provided with the same specifications. when using this power supply, take care of the polarities marked nearby the two-point connector. 49 36/42 ST7MDT1-DVP 5 software features 5.1 tools to help you design, code and debug your applications, and program them on chip, the follow- ing software has been included in the ST7MDT1-DVP development kit: ? st assembly chain ?st7 simulator ? st7 windows debugger ? epromer for st7 mcus a stand-alone st7 instruction help file is also available. in many circumstances, it will help you select the most suitable code for your programs and improve the overall performance of your applications. 5.2 st assembly chain for st7 family the st assembly chain is a cross development system for st7-driven applications. it in- cludes an assembler, a linker, a formatter and a librarian. the information flow is summarized in the chart below: assembler linker librarian formatter debugger with emulator or simulator eprom programmer your source code in assembler .asm .inc .err .obj .lst .map .cod .grp .sym .lib .s19 .asm 50 37/42 ST7MDT1-DVP for more information about the components of the st7 assembly chain refer to the software tools for the st7 family user manual. 5.3 hiware c compiler demonstration chain the hiware c compiler chain for st7 is also available. it makes it possible to develop ap- plications that will be run, debugged at source level, or programmed using the development kit. a demonstration version of the hiware c compiler chain is included in the ST7MDT1-DVP development kit package for evaluation purpose only. 5.4 st7 simulator the st7 simulator is a program that simulates the execution of st7 programs, instruction by instruction. the behaviour of the peripherals is also simulated. note that, in this case, no external hardware is required. you may then debug any of your pro- grams without using the evaluation board of the ST7MDT1-DVP development kit. 5.5 st7 windows debugger you can run the wgdb7 debugger using either of the following: st7 simulator, st7 emulator, st7 development kit. simulation-aided debugging lets you develop and test your application(s) before your hard- ware is finished or available. this could save time and provide you with some flexibility regard- ing your own application development plans. also, this debugging method relieves you from any premature, undesirable, hardware dependency. lastly, this is the cheapest solution. some real-time debugging features such as the tracing facility and the logic analyser function are not available either. nevertheless, you will benefit from new other features such as time measurement, and time-dependent break management. emulation-aided debugging lets you also develop and test your application(s) long before your hardware is finished or available. although it is more hardware-dependent than the sim- ulation option, because emulators have components specific to various microcontroller fami- lies, it presents the major advantage of supporting real-time testing and debugging in the user application board environment. also, it supports the tracing and logic analyser debugging fea- tures that can be used in conjunction with the emulators. 51 38/42 ST7MDT1-DVP the development kit and the emulator debugging capabilities are very close. compared with the simulator and the emulator, the development kit shows some differences, however, summarized in the following table:. table 5. development kit, emulator and simulator debugging features table 6. description debugger+de vkit debugger+em u debugger+sim u hardware test yes yes no loading programs, viewing program details yes yes yes executing loaded programs yes yes yes managing software breakpoints yes yes yes managing hardware breakpoints yes yes yes viewing st7 resources yes yes yes viewing disassembled program code yes yes yes viewing register contents yes yes yes watching symbols, types of variables, expressions yes yes yes entering, assembling mnemonics to emu /simu st7 memory yes yes yes using gdb7 commands yes yes yes choosing emulated/simulated st7 micro name yes yes yes changing st7 emulated/simulated memory mapping yes yes yes displaying and modifying configuration options yes yes yes customising the debugger yes yes yes working with trace buffer no yes no accessing logic analyser information no yes no 52 39/42 ST7MDT1-DVP fore more information on how to debug with any of the above tools, see windows debugger for the st7 family, user manual . 5.6 epromer for st7 mcus epromer is a windows interface that lets you: ? view, edit and save executable files in the hex (intel) and .s19 (motorola) formats, gener- ated by the assembler, linker or c compiler for st microcontrollers. ? program executable files into st microcontrollers. ? view and verify a microcontroller's memory contents. note that epromer is not device dependent. fore more information on how to use epromer, see programming st7 devices on page 27. simulating pin input/output signals n.a. n.a. yes time management no no yes output trigger management yes yes no stack overflow/underflow stop yes no no non-existent memory stop yes no no write protect memory stop yes no no input trigger stop yes no no table 5. development kit, emulator and simulator debugging features table 6. description debugger+de vkit debugger+em u debugger+sim u 53 40/42 index symbols .asm files ..................................................... 36 .cod files ...................................................... 36 .err files ........................................................ 36 .grp files ....................................................... 36 .inc files ....................................................... 36 .lib files ......................................................... 36 .lst files ......................................................... 36 .obj files ....................................................... 36 .s19 files ...................................................... 36 .sym files ..................................................... 36 a adc ............................................................. 28 analog to digital converter ...................... 28 antistatic equipment .................................. 12 application connection ................................ 5 autoexec.bat file ................................. 16 b breakpoints (hardware) ............................ 29 bus events .................................................. 29 c c compiler chain (hiware) ...................... 37 cable for pc connection ........................... 5 clock ............................................................ 26 clock type ................................................... 26 clockin pin .............................................. 26 complementary power supply ................. 35 d debugger (main menu) ............................ 25 debugging (simulation-aided) ................. 37 debugging features ................................. 38 devices in st72251g2 series .................. 5 disabled option (timers) ...................... 28 dos4g environment variable ................ 16 e emulation-aided debugging ..................... 37 enabled option (timers) ....................... 28 environment variables ............................. 16 epromer ................................................ 19, 39 epromer for st7 mcus ............................ 36 events (breakpoints) ................................. 29 external clock ............................................. 26 external output trigger ............................ 30 f finish goods ............................................... 12 h hardware breakpoints .............................. 29 hiware c compiler chain ........................ 37 i i 2 c bus interface .................................... 29 input trigger ............................................... 30 internal clock .............................................. 26 l ld1 led ...................................................... 25 leds (ld1) ................................................. 25 m main menu of debugger ........................... 25 map files ...................................................... 36 memory mapping ....................................... 27 metai environment variable .................. 16 miscellaneous register ............................ 26 modes of operation (cpu) ....................... 25 n normal mode (clock) ................................. 26 nylon clothing ............................................. 12 54 41/42 index o operating modes (clock) .......................... 26 p packages ...................................................... 5 parallel i/o ports ....................................... 27 parallel port of your pc ............................ 34 path option (autoexec.bat) ............ 16 pc connection .............................................. 5 pc parallel port .......................................... 34 pin assignment for probe connection ... 31 power supply .............................................. 35 power supply (complementary) .............. 35 pulse mode (external signal) ................... 30 pulse waveforms ....................................... 27 pulse width modulation ............................ 27 pwm ............................................................ 27 r rom size .................................................... 27 s sdip32 packages ........................................ 5 sdip32 passive probe ................................ 5 serial peripheral interface ....................... 28 simulation-aided debugging .................... 37 slow mode (clock) ..................................... 26 so28 devices ............................................. 19 so28 packages ........................................... 5 spi ............................................................... 28 st assembly chain ............................ 17, 36 st7 simulator ............................................ 36 st7 windows debugger .......................... 36 st72251g2 series summary ................... 5 structure of the ST7MDT1-DVP develop- ment kit ......................................... 6 system mode .......................................... 25 t test pins (evaluation board) .................... 33 testers ........................................................ 12 timers .......................................................... 27 tool-chain ...................................................... 4 triggered break feature ............................ 29 trigin ........................................................ 30 u user application connection ...................... 5 user mode ............................................... 25 w watchdog timer ........................................ 29 waveform mode (external signal) .......... 30 wgdb7 debugger ..................................... 18 wgdb7 emulator ...................................... 18 wgdb7 simulator ..................................... 18 windows epromer ..................................... 19 windows mode (external signal) ............ 30 winee .......................................................... 19 55 42/42 ST7MDT1-DVP notes: information furnished is believed to be accurate and reliable. however, stmicroelectronics assumes no responsibility for the co nsequences of use of such information nor for any infringement of patents or other rights of third parties which may result from its use. no license is granted by implication or otherwise under any patent or patent rights of stmicroelectronics. specifications mentioned in this publicati on are subject to change without notice. this publication supersedes and replaces all information previously supplied. stmicroelectronics prod ucts are not authorized for use as critical components in life support devices or systems without the express written approval of stmicroele ctronics. the st logo is a trademark of stmicroelectronics ? 1998 stmicroelectronics - all rights reserved. purchase of i 2 c components by stmicroelectronics conveys a license under the philips i 2 c patent. rights to use these components in an i 2 c system is granted provided that the system conforms to the i 2 c standard specification as defined by philips. stmicroelectronics group of companies australia - brazil - canada - china - france - germany - italy - japan - korea - malaysia - malta - mexico - morocco - the neth erlands - singapore - spain - sweden - switzerland - taiwan - thailand - united kingdom - u.s.a. 56 |
Price & Availability of ST7MDT1-DVP
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |